Manually Processing Documents

The Manual Process Stage for Rejected Documents constitutes a pivotal phase within our product, addressing scenarios where documents fail to meet defined validations or Region of Interest (ROI) criteria. This comprehensive documentation serves as a guide to proficiently navigate the manual process stage and manually handle and process rejected documents.

The Manual Process Stage for Rejected Documents presents users with an essential solution to manage rejected documents that deviate from specified validations or ROI parameters. By leveraging this module, users can effectively process rejected documents manually, ensuring accurate data extraction and alignment.

Key Features of the Manual Process Stage for Rejected Documents

The Manual Process Stage for Rejected Documents encompasses the following key features:

Document Rejection Handling: The module enables users to address rejected documents that do not match defined validations or ROI.

Manual Processing: Users can manually handle and process rejected documents further to achieve accurate data extraction.

Note:

If you encounter any issues, contact your system administrator.

 

Accessing manual handling page

To access the manual handling page, follow these steps:

  1. In the main menu, under Documents Processing, click Manual Process. The Manual Handling page opens.

During the data extraction process, if the information related to an ontology field is present in the database, it will be directly fetched from the database. The Knowledge master enables you to maintain information related to documents in a database. MoreClosedFor the incomplete field details, you can click and capture the required data on the appropriate fields, and there may be instances where some details do not get captured by click and capture; in such cases, you need to enter the details manually until you find the green tick icon.

Note:

In the case of multiple documents, the auto splitter splits them based on the document classification or the splitter field mentioned in the ontology.

Suppose the document is not split into the correct pair and is sent to MI. The user can identify if it has arrived after splitting by looking for the parent document id (if available) mentioned in brackets, as shown below.

 

Understanding the manual handling UI

TruCap+ includes several colors indicating elements to help detect the errors which require manual intervention on the Manual handling page.

The colour indication is the field outline/band color for textbox/dropdown reflected in MI/QC. The user can customize the color of his choice by configuring the settings under the MI field background colour section of the Application settings section.

The MI page is divided in to 4 sections — Source Identifier (optional), Header, Detail (table), and Footer. The colour indications explained are common for all 4 sections.

 

Quick access toolbar

The below image explains some handy tools available on the upper-right corner of the Manual Handling page.

Hover-over the above image to know about the available features.

Click on the individual drop-downs for a detailed explanation of the available features.

 

Accessing MI page settings

On the right side of the Manual Handling page, when you click the settings icon, the following four toggle switch are displayed.

  • View original document: The images displayed on the MI page are processed images. To view the original image, turn on the View original document toggle switch.

  • Fields requiring attention: Turn on to use the TAB button functionality for the affected fields on MI and QC page. Turn off to use the TAB button as a default functionality for all the fields. The Tab button setting is applicable at a user level. Based on the requirement, any user can turn on to use the functionality.

    Note:

    During the manual intervention, based on the Fields requiring attention setting, the default cursor position gets focused on the affected field, which needs a priority check. The cursor gets focused in a sequential order depending on the number of affected fields.

    Users can use the TAB button to move to the next suspicious field. This feature is applicable for Header, Detail (In the case of Table, default cursor position navigates to the next row), and Footer. The field is considered suspicious in the following scenarios:

    • When any mandatory field is blank

    • When any field had been set as "Stop and confirm" under ontology

    • When there is any multi-suspected field

    • When the validation has failed for any particular field

    • When any field had been set as "Must Focus" under ontology

    When you enable the Fields requiring attention toggle switch, the Change Tab Preference? dialog box opens.

    Click Yes to modify tab preference setting.

  • Display field panel on right: On clicking this toggle switch, the left side panel, which contains Header, Detail, and Footer tabs, moves to the right side of the screen. It is a one-time setting.

  • Auto Save: If the user enables this toggle switch, the document gets automatically saved after a set time. Refer auto save time under Manual Intervention settings.

 

NEXT

Now that you have manually processed a document, let's quality check it.

 

Defining rules

Creating fields

Creating category

Creating project

Exporting ontology

Importing ontology

Updating ontology

TruCap+ Studio

Manual processing

Manual splitting

Integrated documents processing

Quality check

Input/Output setup

Field types

Operations dashboard

QC dashboard

Document monitor

Accessing menus